Troubleshooting email notifications

Can you send a general test email?

This checks that you can send emails using the E-mail settings you have entered.

Open: System Administration > Messaging > E-Mail Settings.

Click Edit.
Enter an email address in the Send E-Mail To box, and click Send.

An email is sent to the address specified.

Have you entered the correct email port and does your email server use SSL?

Check your email server settings in Sage 200 System Administration.

Open: System Administration> Messaging > E-Mail Settings.

Click Edit.
Check your Server Port Number.

If required, select Server requires secure connection (SSL).

The following table shows the Port Number and SSL requirements for some common email servers.

	E-Mail Server	Port Number	Requires SSL
Hotmail	smtp.live.com	587	Yes
Gmail	smtp.gmail.com	587	Yes

Tip: You can find information about common email server settings online, for example, the email address manager website.

Does your anti-virus application allow bulk e-mail submissions?

Sometimes your anti-virus software will block the notifications email via your server. Check your anti-virus software settings.

Have you chosen to use email notifications in the Sage 200 System Administration application?

Open: System Administration > Messaging > Purchase Order Authorisation.

Click Edit.
Select Use Email Notifications.
Click OK.

Is your Sage 200 user account set up to receive emails and have you entered a valid email address?

Check the Sage 200 user account Properties.

You can check the log files for more information.

Have you set up an alternative authoriser for the Sage 200 user?

In your Sage 200 application, you can specify another Sage 200 account as an alternative authoriser. This alternative Sage 200 user will receive the notification messages for the original Sage 200 user.

Open: Purchase Order Processing > POP Utilities > System Set Up > Maintain Alternative Authorisers.

Check if the Sage 200 user has an Alternative set up.

On Premise deployments only - Have you checked the log files for further information about where the services are failing?

Sage 200 records information about where the service is failing in the Sage 200 Services log file.

To check the Sage 200 Services:

To make sure the log file contains more detailed information, open the following file using the Notepad application: C:\Inetpub\Sage 200 App Service\Sage200Services\Web.config.
Change the <level value> in the <log4net> section to Debug. This is set to warn by default. For example:
```
<log4net>
<logger name="ApplicationLog">
<level value="Debug" />
<appender-ref ref="LogFileAppender" />
</logger>
```
The log file will now contain more detailed information.

On some systems, due to security constraints, you may also need to create an Empty.log file. The Windows user account the web service runs under also needs permission to write to the log file and the Empty.log file.
To check the details of any errors in the log file, open the following file: C:\Inetpub\Sage 200AppService\Sage200Services\Log\Sage200Services.log